Photosharing server filters for automatic storage and sharing of digital files

ABSTRACT

A method and system for providing on online file-service that automatically stores and organizes digital files. The method and system include providing the server with a set of trigger handlers that are each configured to perform a particular action on a digital file. The user may log into the server and specify attribute criteria for each of the trigger handlers. Digital files uploaded by the user are received by the server, wherein each file has a plurality of attributes associated therewith. The attributes of each file are then compared with the attribute criteria entered by the user for each of the trigger handlers. And upon a match, the corresponding trigger handler is invoked, such that actions are automatically performed on the digital files.

FIELD OF THE INVENTION

[0001] The present invention relates to electronic storage and sharing of digital files, and more particularly to a method and system for providing photosharing server filters for automatic storage and organization of digital images of different types.

BACKGROUND OF THE INVENTION

[0002] Users who wish to store and organize digital files including images, music, and video have two basic options. One option is to store and organize the digital files in containers on their PCs using a standard tree-based directory service provided by most computer operating systems (e.g., Windows™, UNIX™, Macintosh™). File system directories are capable of storing digital files of any Mime type. Mime type is a file identification based on the Mime encoding system and is a standard for identifying content of a file. The major Mime types are applications, audio, image, text, and video. Typically, anyone with permission to write to a directory may store any file there regardless of the Mime type of the file.

[0003] The second option is to store digital files into containers, such as albums in online photosharing sites, and containers controlled by software applications, e.g., photo collection applications, music collection applications, and video collection applications, for example.

[0004] Unlike file system directories, however, containers in the second option are capable of storing and handling only specific types of digital files. For example, only digital images can be uploaded to online photosharing sites or imported into photo collection applications, while only music files can be handled by music collection applications. In these types of applications, users cannot specify the specific media types that will be stored or shared. For example, in conventional online photosharing, a user is unable to store both images and video clips in a common album.

[0005] With respect to conventional photosharing sites specifically, not only is the user limited to uploading only image files, but once the images are uploaded to site, the user must manually organize the images by creating new photo albums and then moving selected images to the appropriate photo albums.

[0006] Once the images are manually stored and organized, the user may then notify others of the images using one of two methods. In the first method, the user sets preferences for the album specifying what users have permission to view the album, and personally informs each person of the web address of the album. In the second and more common method, the user types-in the e-mail addresses of each person the user wants to view the album and the photosharing site automatically sends an e-mail inviting recipients to view the album by clicking on the enclosed URL.

[0007] Overtime, users find manually organizing files and sending notifications image-by-image to be burdensome and tedious. Accordingly, what is needed is an improved method and system for storing and organizing digital files. The present invention addresses such a need.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008]FIG. 1 is a block diagram illustrating an online file-service system that automatically stores and organizes digital files in accordance with a preferred embodiment of the present invention.

[0009]FIG. 2 is a flow diagram of the process for automatically storing and organizing digital files uploaded to file-service site in accordance with a preferred embodiment of the present invention.

[0010]FIG. 3 is a form corresponding to an Album creation/population trigger.

[0011]FIG. 4 is a form corresponding to a Notification trigger.

[0012]FIG. 5 is a form corresponding to a Print trigger.

[0013]FIG. 6 is a form corresponding to a Postcard Trigger.

SUMMARY

[0014] The present invention is a method and system for providing on online file-service that automatically stores and organizes digital files. The method and system include providing the server with a set of trigger handlers that are each configured to perform a particular action on a digital file. The user may log into the server and specify attribute criteria for each of the trigger handlers. Digital files uploaded by the user are received by the server, wherein each file has a plurality of attributes associated therewith. The attributes of each file are then compared with the attribute criteria entered by the user for each of the trigger handlers. And upon a match, the corresponding trigger handler is invoked, such that actions are automatically performed on the digital files.

[0015] According to the method and system disclosed herein, the user is allowed to configure the trigger handlers to take desired actions on the files, such as creating containers and populating the containers with uploaded files that meet the users specified criteria, sending automatic email notifications to addresses entered the by the user, and printing files created on certain dates, for example.

DETAILED DESCRIPTION OF THE INVENTION

[0016] The present invention relates to a method and system for providing a file service that automatically stores and organizes digital files of different Mime types. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiments and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features described herein.

[0017] The present invention provides an improved method and system for storing and organizing digital files in which files are uploaded to a server for storage, and the server automatically stores and organizes the files based on attributes of the files specified by the user. In addition, files of different types may be stored in the same container.

[0018]FIG. 1 is a block diagram illustrating an online file-service system 10 that automatically stores and organizes digital files in accordance with a preferred embodiment of the present invention. The system 10 includes one or more client devices 12 that access a file-service site 14 over a network 18, such as the Internet. Once connected to the Internet, the client device 12 has the capability of uploading digital files 16 to the file-service site 14 for storage and/or for receiving digital files 16 from the file-service site 14 for display.

[0019] A client device 12 refers to an electronic device capable of storing digital files and communicating over a network 18, such as PCs. The digital files 16 may have different Mime types, including text, images, audio, and movie files. In a preferred embodiment, the client devices 12 are browser-based, although non-browser-based devices may also be supported using a specialized application (not shown) executing on the device 12.

[0020] In one preferred embodiment, the file-service site 14 is a photosharing site, and the type of digital files 16 that are uploaded to the site are predominately digital images, but also include video clips, and audio. In the photosharing embodiment, a client device 12 may also include any electronic device capable of storing digital images and/or video, such as photo kiosks, web-enabled digital cameras, PDAs, and cellphones, for example.

[0021] In a preferred embodiment, some or all of the digital files 16, particularly images, have metadata 22 associated with them that describes and/or categorizes the file 16. The metadata 22 may be included within the files 16, or be stored in a separate file 16. Other types of digital files 16 may also include metadata 22, such as HTML and XML documents, for example.

[0022] In accordance with one aspect of the present invention, the online file-service site 14 can be configured by the user to store different types of files 16 in the same container (albums in a preferred embodiment), and to automatically perform actions on each file 16 based on specified attributes of the file 16, including the Mime type.

[0023] To accomplish these functions, the file service site 14 comprises at least one server 20 that includes a web server/upload manager 24, a metadata filter 26, a user accounts and preferences database 28, a digital file and album database 30, and one or more trigger handlers 32. The web server/upload manager 24 accepts connections from the client device 12 and receives uploaded files 16. The web server/upload manager 24 also handles interactions from web browsers (not shown) for setting user preferences and requests to view container albums.

[0024] The trigger handlers 32 are routines that automatically perform respective actions on the files 16. In a preferred embodiment, there are categories of trigger handlers 32 that include container creation/population handlers, notification handlers, printing handlers, and postcard handlers. The user accesses the server 20 over the web to configure filter preferences, which are rules that govern when the trigger handlers 32 are called to operate on a particular image based on attributes of the file. In a preferred embodiment, filter preferences are stored in the user accounts and preferences database 28.

[0025] As the files 16 are uploaded, the metadata filter 26 extracts the metadata 22 associated with each uploaded file 16, and if the metadata 22 matches any of the user-configured file attributes of the filter preferences stored in the user preferences database 28, the appropriate trigger handler 32 is called to automatically perform its operation on the file 16, such as creating an album and storing the file 16 in that album.

[0026]FIG. 2 is a flow diagram of the process for automatically storing and organizing digital files uploaded to the file-service site 14 in accordance with a preferred embodiment of the present invention. The process begins in step 200 when a user logs into the file-service site 14 via a web browser and creates an account. All the user's account information, including user ID, is stored in the user account and preferences database 28.

[0027] Once the user has become a member of the file-service 14, the file-service 14 displays a series of configuration forms in step 202 for the user to enter filter preferences that control when each of the trigger handlers 32 are called when the user uploads files 16. In a preferred embodiment, the filter preferences forms are specific to the different types of trigger handlers 32 available, and have fields for a user to enter attribute criteria for the images that will be used to filter the files 16 to the appropriate trigger handler upon upload.

[0028]FIGS. 3-6 are diagrams illustrating example filter preference forms. FIG. 3 is a form corresponding to an Album creation/population trigger. FIG. 4 is a form corresponding to a Notification trigger. FIG. 5 is a form corresponding to a Print trigger. And FIG. 6 is a form corresponding to a Postcard Trigger.

[0029] Referring to FIG. 3, each form 40 includes two sections, an Attribute Criteria section 42, and an “Actions” section 44. The Attribute Criteria section 42 allows the user to specify which file attributes and metadata fields from uploaded files 16 are to be matched and the nature of the match for invoking the proper trigger handler 32. In one embodiment, the Attribute Criteria section 42 includes a column for the user to enter metadata field names 46, a column for entering operators 48, and a column for entering values 50 for the corresponding field name.

[0030] The Actions section 44 of the filter preferences form 40 is specific to the trigger handler 32, but allows the user to specify what actions are to be taken in response to a match, such as the creation/population of a specified album, for instance.

[0031] Referring again to FIG. 2, after the user completes the filter preferences forms 40, in step 204 the filter preferences are stored in the user account and preferences database 28. Anytime thereafter, the user may upload files from the client device 12 to the file service site 14 in step 206. In step 208 the web server/upload manager 24 receives the files 16 and passes them to the metadata filter 26 along with the user ID of the user. In step 210, the metadata filter 26 uses the user ID to retrieve the filter preferences for the user. In step 212, the metadata filter 26 extracts the metadata 22 from the files 16 as they are received and compares the extracted metadata 22 with the attribute criteria 42 specified by the user's filter preferences. When the metadata filter 26 detects a match in step 214, the metadata filter 26 invokes the corresponding trigger handler 32, such that actions defined by the trigger handler 32 and the user preferences are automatically performed on the digital files 16.

[0032] As shown in FIG. 3, for example, the user has entered preferences that will configure the server 20 to automatically store files matching the criteria in the Attribute Criteria section 42 into two albums named “Christmas 2002” and “December 2002.” Any files 14 uploaded by the user whose metadata “date” field has values between “12-01-02” and “12-31-02” and whose metadata “category” field “contains” the value “holiday,” will be stored in the two specified albums. If the albums do not yet exist, then the server 20 will create them. For albums, the Actions section 44 also allows the user to specify what Mime types the albums may store. If “All” is selected, then the albums will be able to store and display files of any type.

[0033] Other examples of file preferences forms are shown in FIGS. 4-6. The Attribute Criteria section 42 on these forms is similar to that shown in FIG. 3, and like components have like reference numerals. Referring to FIG. 4, the filter preferences form 40′ for the notification trigger is shown according to the present invention. The notification trigger allows the user to configure the server 20 to automatically send out notifications regarding the arrival of certain files 16 to specified third parties by email, pager, and/or facsimile. The filter preferences form 40′ shown in FIG. 4 is for email notification. The Actions section 44 of the form 40′ includes a field 60 for entering the email addresses of recipients, a field 62 for choosing an email template, a field 64 for adding an optional message to the email, and a check box 66 designating whether to attach the file 16 or add a link to the file 16. The form 40′ may also include sending options 68 for designating how often the email notification is sent when a matching file 16 is detected. The options 68 may include sending the email upon every match, sending one email a day for all matches, or sending all notifications once per week.

[0034] Referring to FIG. 5, the filter preferences form 40″ for the Print trigger is shown. The Print trigger automatically prints the files 16 matching the attribute criteria 42. The Actions section of the form 40″ includes fields 70 for the user to specify the number of prints per image, and the size of the print. Also, included are sending options 72 and a field 74 for designating recipients.

[0035] Referring to FIG. 6, the filter preferences form 40′″ for the Postcard Trigger is shown. The Postcard trigger walks the user through creating an electronic postcard that incorporates a matching image and that is then sent to a specified recipient. The Actions section 44 of the form 40′″ includes fields 80 for the user to select a postcard, a field 82 for the email address of the recipients, a field 84 for the number of times to send, and a field 86 for when the postcard should be sent.

[0036] The present invention has been described in accordance with the embodiments shown, and one of ordinary skill in the art will readily recognize that there could be variations to the embodiments, and any variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims. 

We claim: 1 A method for providing on online file service that automatically stores and organizes digital files, the method comprising the steps of: (a) providing the server with a set of trigger handlers that are each configured to perform a particular action on a digital file; (b) allowing the user to access the server and configure the trigger handlers by specifying attribute criteria for one or more of the trigger handlers; (c) receiving digital files uploaded to the server, wherein each file has a plurality of attributes associated therewith; (d) comparing the attributes of each file with the attribute criteria entered by the user for each of the trigger handlers; and (e) upon a match, invoking the corresponding trigger handler, such that actions are automatically performed on the digital files. 2 The method of claim 1 wherein step (a) further includes the step of: providing categories of trigger handlers, including any combination of a container creation/population handler, a notification handler, a print handler, and a postcard handler. 3 The method of claim 2 wherein step (b) further includes the step of: allowing the user to configure the container creation/population handler to cause the server to automatically store uploaded files matching the attribute criteria into a specified container. 4 The method of claim 3 wherein step (b) further includes the step of: allowing the user to configure the container creation/population handler to automatically create the specified container if necessary. 5 The method of claim 4 wherein step (a) further includes the step of: allowing the user to configure the creation/population handler to store files of different Mime types in the same container. 6 The method of claim 2 wherein steps (c) and (d) further includes the step of: extracting any metadata associated with each uploaded file, and comparing the metadata with the attribute criteria entered by the user for each of the trigger handlers. 7 The method of claim 3 wherein step (b) further includes the step of: creating a user account for the user, including a user ID. 8 The method of claim 4 wherein step (b) further includes the step of: saving the attribute criteria entered by the user for each of the trigger handlers as filter preferences. 9 The method of claim 8 wherein step (b) further includes the step of: storing the filter preferences with the user account. 10 The method of claim 9 wherein step (c) further includes the step of: when files are uploaded, using the user ID of the user to retrieve the user's filter preferences. 11 The method of claim 2 wherein step (b) further includes the step of: displaying a series of configuration forms for the user to enter the attribute criteria. 12 The method of claim 11 wherein step (b) further includes the step of: providing each form with a first section for allowing the user to specify which file attributes and metadata fields from uploaded files are to be matched and the nature of the match, and a second section for allowing the user to specify what actions are to be taken in response to a match. 13 A method for providing an online photosharing service that automatically stores and organizes digital image files, the method comprising the steps of: (a) providing the server with a set of trigger handlers that are each configured to perform a particular action on an image file; (b) allowing the user to access the server and configure the trigger handlers by specifying attribute criteria for one or more of the trigger handlers; (c) receiving image files uploaded to the server, wherein each image file has a plurality of attributes associated therewith; (d) comparing the attributes of each image file with the attribute criteria entered by the user for each of the trigger handlers; and (e) upon a match, invoking the corresponding trigger handler, such that actions are automatically performed on the image files. 14 The method of claim 13 wherein step (b) further includes the step of: providing categories of trigger handlers, including any combination of a container creation/population handler, a notification handler, a print handler, and a postcard handler. 15 The method of claim 14 wherein step (b) further includes the step of: allowing the user to configure the container creation/population handler to cause the server to automatically store uploaded files matching the attribute criteria into a specified container. 16 The method of claim 15 wherein step (b) further includes the step of: allowing the user to configure the container creation/population handler to automatically create the specified container if necessary. 17 The method of claim 16 wherein step (a) further includes the step of: allowing the user to configure the creation/population handler to store files of different Mime types in the same container, including any combination of images, video, audio, and text. 18 The method of claim 14 wherein steps (c) and (d) further includes the step of: extracting any metadata associated with each uploaded image file, and comparing the metadata with the attribute criteria entered by the user for each of the trigger handlers. 19 The method of claim 15 wherein step (b) further includes the step of: creating a user account for the user, including a user ID. 20 The method of claim 16 wherein step (b) further includes the step of: saving the attribute criteria entered by the user for each of the trigger handlers as filter preferences. 21 The method of claim 20 wherein step (b) further includes the step of: storing the filter preferences with the user account. 22 The method of claim 21 wherein step (c) further includes the step of: when files are uploaded, using the user ID of the user to retrieve the user's filter preferences. 23 The method of claim 14 wherein step (b) further includes the step of: displaying a series of configuration forms for the user to enter the attribute criteria. 24 The method of claim 23 wherein step (b) further includes the step of: providing each form with a first section for allowing the user to specify which file attributes and metadata fields from uploaded files are to be matched and the nature of the match, and a second section for allowing the user to specify what actions are to be taken in response to a match. 25 A computer-readable medium containing program instructions for providing on online file service that automatically stores and organizes digital files, the instructions for: (a) providing the server with a set of trigger handlers that are each configured to perform a particular action on a digital file; (b) allowing the user to access the server and configure the trigger handlers by specifying attribute criteria for one or more of the trigger handlers; (c) receiving digital files uploaded to the server, wherein each file has a plurality of attributes associated therewith; (d) comparing the attributes of each file with the attribute criteria entered by the user for each of the trigger handlers; and (e) upon a match, invoking the corresponding trigger handler, such that actions are automatically performed on the digital files. 26 The computer-readable medium of claim 25 wherein instruction (a) further includes the instruction of: providing categories of trigger handlers, including any combination of a container creation/population handler, a notification handler, a print handler, and a postcard handler. 27 The computer-readable medium of claim 26 wherein instruction (b) further includes the instruction of: allowing the user to configure the container creation/population handler to cause the server to automatically store uploaded files matching the attribute criteria into a specified container. 28 The computer-readable medium of claim 27 wherein instruction (b) further includes the instruction of: allowing the user to configure the container creation/population handler to automatically create the specified container if necessary. 29 The computer-readable medium of claim 28 wherein instruction (a) further includes the instruction of: allowing the user to configure the creation/population handler to store files of different Mime types in the same container. 30 The computer-readable medium of claim 26 wherein instructions (c) and (d) further includes the instruction of: extracting any metadata associated with each uploaded file, and comparing the metadata with the attribute criteria entered by the user for each of the trigger handlers. 31 The computer-readable medium of claim 27 wherein instruction (b) further includes the instruction of: creating a user account for the user, including a user ID. 32 The computer-readable medium of claim 28 wherein instruction (b) further includes the instruction of: saving the attribute criteria entered by the user for each of the trigger handlers as filter preferences. 33 The computer-readable medium of claim 32 wherein instruction (b) further includes the instruction of: storing the filter preferences with the user account. 34 The computer-readable medium of claim 33 wherein instruction (c) further includes the instruction of: when files are uploaded, using the user ID of the user to retrieve the user's filter preferences. 35 The computer-readable medium of claim 26 wherein instruction (b) further includes the instruction of: displaying a series of configuration forms for the user to enter the attribute criteria. 36 The computer-readable medium of claim 35 wherein instruction (b) further includes the instruction of: providing each form with a first section for allowing the user to specify which file attributes and metadata fields from uploaded files are to be matched and the nature of the match, and a second section for allowing the user to specify what actions are to be taken in response to a match. 